Summary

Stage H1 of the mod-utils v6 adoption program's wave 4 (maintainer-approved): the mechanical
generation pin for Hinode v3. Bumps Hinode's own module path and the module-generation
majors per the decision package,
vendors, and rebuilds the exampleSite clean. Argument-warning cleanup is explicitly out of
scope for this PR — see the warnings inventory below, which is H2's work list.

Pin table (decision package §1)

mod-bootstrap, mod-csp, mod-katex, mod-google-analytics, mod-cookieyes, and mod-docs
stay on their current lines — none of them depend on mod-utils, and mod-docs is
generation-agnostic (API-stable across v5/v6).

Migration notes

This is a path-bump-only PR. Hinode's own InitArgs.html call sites (~110 of them) are
not migrated to the Args.html API here — that is a deliberate H2-stage decision (see
decision package §2.2: migrate the high-traffic shortcodes/partials, keep the shim for the
tail). See gethinode/mod-utils#334 and mod-utils' v5→v6 migration notes for the engine change
itself.

Generation-mixing warning (decision package §5)

A v5-generation site that adds one v6-generation module flips its entire site onto the v6
validation engine: Hugo resolves a single mod-utils, and import order decides who wins. In
Hinode's own module config every module import precedes mod-utils, so a v6-carrying module
always wins. The engines are API-compatible, but behavior deltas (defaults now apply, new
warnings) arrive wholesale, not incrementally. Adopt the generation together, via this
major — do not cherry-pick individual v6 modules onto a v2 Hinode site.

Rendered-output deltas (decision package §2.5)

Per the visual baselines captured during the module-wave program, expect (and this PR's own
visual gate confirms, see below) these intended rendered-output changes once the v6 engine's
defaults actually apply, relative to the v5-generation site:

• section-title width: w-100 → col-12 col-md-8
• hero/heading width default: 8
• illustration.width default: 8 (smaller hero/illustration images where content omits
  widths)

These are pinned in the program's visual baselines with per-page justifications; this PR's own
candidate build was compared against the v6-engine baseline (which already reflects these
deltas), not the v5 baseline, so no new diffs are expected from them here.

Warnings inventory (H1 deliverable — H2's work list)

Full categorized table in .superpowers/visual/wave4-hinode-h1-report.md in the driver's
program workspace (not committed to git, per the program's baseline-workspace convention —
see tests/visual/README.md). Summary: build exits 0, zero ERROR lines, 533 top-level WARN
lines (517 Invalid arguments headers + 16 other Hugo-core WARN lines), the 517 headers
carrying 1,045 individual argument-detail lines that collapse to 57 distinct
[component] argument ... patterns, plus 13 distinct non-argument WARN messages.

• (a) Hinode call-site bug — 53 patterns, 991 occurrences. Overwhelmingly one root
  mechanism: Hinode's own un-migrated InitArgs.html call sites forward their own
  possibly-unset argument values (which now surface as literal ""/wrong-typed zero-values
  under the v6 engine instead of being silently coerced) into a nested partial's own
  validated argument dict — e.g. card-group.html passing "color" $args.color straight
  through into card.html. Traced with file:line evidence for representative cases
  (card-group.html, image-set.html, sidebar.html, bundlev2.html callers). Also
  includes one structure-file gap fully fixable inside this repo: data/structures/link.yml
  doesn't declare outline, even though assets/links.html reads .outline off every link
  item.
• (b) exampleSite content issue — 0 patterns. None isolated to content-only causes; every
  pattern traced back to a call-site or schema mechanism.
• (c) engine/deprecation notice — 13 patterns (all non-argument WARN lines: Hugo-core
  config-key/method deprecations, identical before/after, unrelated to mod-utils).
• (d) other — 4 patterns, 54 occurrences, all pre-existing mod-utils shared-type schema
  gaps, already tracked as maintainer follow-ups in decision package §3 (not fixable inside
  Hinode or mod-blocks alone): testimonials[N] unsupported icon, video unsupported
  media_id and color (this PR's build additionally surfaces color as undeclared on the
  shared video
  type, beyond the id/media-id gap decision package §3 already named).

Gates

• hugo mod graph -s exampleSite: every gethinode edge on its new-generation major, zero
  old-major edges.
• pnpm run build:example: exit 0, zero ERROR lines (532-533 WARN lines, inventoried above).
• Visual regression (tests/visual/visual.mjs) vs. the driver's v6-engine baseline
  (.superpowers/visual/baseline-v6): 41/42 clean, 1 flagged — the known mermaid
  render-race flake (en_docs_components_mermaid.png, 0.248% diff ratio), consistent with the
  documented 0.1-0.3% residual flake. Full report triaged in the H1 report doc.

Not in scope for this PR

• Hinode's own InitArgs → Args.html call-site migration (H2).
• Fixing any of the inventoried warnings (H2).
• The mod-utils shared-type schema gaps (maintainer decision, decision package §3).
• Downstream sites/themes (template, version-demo, customization-demo, theme-agency,
  gethinode.com) — gated on this PR's release.

This PR is not merged. H2 adds commits to this same branch for the warnings cleanup.

🤖 Generated with Claude Code

Stage H2 — warnings-backlog cleanup

Adds 7 commits on top of H1's mechanical pin: bumps mod-utils to v6.2.0 (the release
containing PR #337's video.color member, on top of v6.1.0's PR #336
testimonials.icon/video.media-id), then fixes the category (a) call-site bugs from H1's
warnings inventory and removes the now-dead deprecated-twin/default-pipe patterns. Full
evidence: .superpowers/visual/wave4-hinode-h2-report.md.

Warnings: before → after

46 of H1's 53 numbered category-(a) patterns (964 of 991 occurrences) fixed at their Hinode
call sites — predominantly raw .Get/GetArgParent locals or ad hoc ""/false initializers
forwarded into a nested Args-validated partial instead of the caller's own already-validated
$args envelope (an explicit "" is now a real, rejected value under the v6 engine; only a
true nil is "absent" and eligible for the schema default to apply). Two new Hinode-owned
helpers (utilities/OmitEmpty.html, utilities/ToStringSlice.html) centralize the fix; the
data/structures/table.yml breakpoint: default: "" bug (single highest-count pattern, 70-80
occurrences) was a genuine structure-file default error, fixed directly.

7 patterns (27 occurrences) are NOT fixable in this repo — deeper tracing than H1's initial
categorization showed these are upstream:

• links[N] outline (section-title/links/hero/about, 12 occurrences): the shared links
  type in mod-utils's vendored data/structures/_types.yml lacks outline — not a Hinode
  link.yml gap as originally attributed (that file only governs the standalone shortcode,
  which doesn't even forward outline). Same class as the already-fixed testimonials.icon/
  video.media-id/video.color gaps; recommend the same upstream-PR treatment.
• hero-image justify, table pagination, card-group gutter (9 + 2-3 + 2-3
  occurrences): three literal-""-forwarding call-site bugs in mod-blocks v2.0.0
  (assets/hero.html, list.hugo.html, video-message.hugo.html) — same bug class this PR
  fixes throughout Hinode, just in the already-released mod-blocks module. Out of this stage's
  authorized scope (hinode repo only).

Visual triage

40/42 pages clean (≤0.0071% diff). 2 flagged, both triaged:

• mermaid (0.35% diff) — the documented pre-existing render-race flake, accepted per the
  program's known-flake allowance.
• card (dimension mismatch, +48px) — intended. Isolated via before/after HTML-source
  diff (not just pixels): header-style's schema default (full) now correctly applies where
  raw "" forwarding previously bypassed it entirely, so several cards' header caption
  (date/reading-time/tag line) now renders instead of staying empty — a real rendering-defect
  fix, not a regression. A same-mechanism, functionally-inert duplicate p-0 class (schema
  default collides with a pre-existing hardcoded literal) was also found and left as-is
  (zero visual effect, out of this PR's scope). Full mechanism write-up in the H2 report.

Commits

build(deps) mod-utils bump · fix(structures) table breakpoint default · feat(utilities)
OmitEmpty/ToStringSlice helpers · fix(images) · fix(cards) · fix(scripts) ·
fix(sidebar).

Still not merged — driver review pending.

Stage H3 — upstream pins close the backlog

acb3bdd1 chore: pin mod-utils v6.3.0 and mod-blocks v2.0.1 — the two upstream releases
fixing everything H2 flagged as out-of-repo (links[].outline shared-type member; mod-blocks'
hero-image justify / list pagination / video-message gutter empty-forwards). Result:
ZERO Invalid arguments warnings (down from 22-27 after H2, 504 after H1); the only
remaining WARN output is the 13 distinct pre-existing Hugo-core deprecation notices (16 lines,
byte-identical to the pre-program state). Verified deterministic across two builds, exit 0.

Visual: 40/42 clean vs baseline-v6, same two flags as H2 — mermaid (0.46%, known render-race
flake; H3-vs-H2 shot comparison shows the same page flickering at 0.107%, confirming flake) and
the card docs page (+65px vs H2): the auto-generated argument-reference table now documents the
new outline link member — intended, mechanism verified by HTML diff.